Skip to content
This repository was archived by the owner on Mar 17, 2025. It is now read-only.

Fix installation of Project File Tools on Visual Studio 2019 updates - #62

Merged
KirillOsenkov merged 1 commit into
dotnet:masterfrom
Megasware128:patch-1
Jan 9, 2020
Merged

KirillOsenkov merged 1 commit into
dotnet:masterfrom
Megasware128:patch-1

Conversation

@Megasware128

Copy link
Copy Markdown
Contributor

Unlike other VS releases in 2019 updates minor point releases are being used (src). So I changed the range like specified in this blog post. This fixes issue #61.

@passuied

Copy link
Copy Markdown

Please merge this PR for benefit of others

@mlorbetske mlorbetske left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contributing this :)

@mlorbetske

Copy link
Copy Markdown
Contributor

@madskristensen

@madskristensen

Copy link
Copy Markdown
Collaborator

@mlorbetske I can't approve PRs on this repo. @jaredpar can you? I can do the build and release a new version to the Marketplace once it's merged

@Grepsy

Grepsy commented Sep 4, 2019

Copy link
Copy Markdown

Ping! Hope we can move this forward.

@Tasteful

Copy link
Copy Markdown

@madskristensen Can you find someone else that can approve this if @jaredpar not have the possibility?

@madskristensen

Copy link
Copy Markdown
Collaborator

@davkean ?

@passuied

Copy link
Copy Markdown

Just a side note that my PR (#64) also addresses the VS 2019 update.
I know we're still looking for a repo owner to merge though...
Is there an option to fork this into a different repo with a different owner to get through this hurdle?

@KirillOsenkov
KirillOsenkov merged commit 5b4e7f2 into dotnet:master Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants